IRIX Base Documentation 2001 May

home *** CD-ROM | disk | FTP | other *** search

/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / u_man / cat1 / csplit.z / csplit

Wrap

Text File | 1998-10-20 | 8.7 KB | 199 lines

ccccsssspppplllliiiitttt((((1111)))) ccccsssspppplllliiiitttt((((1111)))) NNNNAAAAMMMMEEEE _cccc_ssss_pppp_llll_iiii_tttt - context split SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS _cccc_ssss_pppp_llll_iiii_tttt [_----_ssss] [_----_kkkk] [_----_ffff _p_r_e_f_i_x] [_----_nnnn _n_u_m_b_e_r] _f_i_l_e _a_r_g_1 [... _a_r_g_n] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN _cccc_ssss_pppp_llll_iiii_tttt reads _f_i_l_e and separates it into _n+1 sections, defined by the arguments _a_r_g_1..._a_r_g_n. By default the sections are placed in _xxxx_xxxx_0000_0000..._xxxx_xxxx_n (_n may not be greater than 99). These sections get the following pieces of _f_i_l_e: 00: From the start of _f_i_l_e up to (but not including) the line referenced by _a_r_g_1. 01: From the line referenced by _a_r_g_1 up to the line referenced by _a_r_g_2. _.... _.... _.... _n: From the line referenced by _a_r_g_n to the end of _f_i_l_e. If the _f_i_l_e argument is a _----, then standard input is used. _cccc_ssss_pppp_llll_iiii_tttt processes supplementary code set characters, and recognizes supplementary code set characters in the _p_r_e_f_i_x given to the _----_ffff option (see below) according to the locale specified in the _LLLL_CCCC______CCCC_TTTT_YYYY_PPPP_EEEE environment variable (see _LLLL_AAAA_NNNN_GGGG on _eeee_nnnn_vvvv_iiii_rrrr_oooo_nnnn(5)). In regular expressions, pattern searches are performed on characters, not bytes, as described on _eeee_dddd(1). The options to _cccc_ssss_pppp_llll_iiii_tttt are: _----_ssss _cccc_ssss_pppp_llll_iiii_tttt normally prints the number of bytes in each file created. If the _----_ssss option is present, _cccc_ssss_pppp_llll_iiii_tttt suppresses the printing of all byte counts. _----_kkkk _cccc_ssss_pppp_llll_iiii_tttt normally removes created files if an error occurs. If the _----_kkkk option is present, _cccc_ssss_pppp_llll_iiii_tttt leaves previously created files intact. _----_ffff _p_r_e_f_i_x If the _----_ffff option is used, the created files are named _p_r_e_f_i_x_0000_0000_...._...._...._p_r_e_f_i_x_n. The default is _xxxx_xxxx_0000_0000..._xxxx_xxxx_n. Supplementary code set characters may be used in _p_r_e_f_i_x. _----_nnnn _n_u_m_b_e_r Use _n_u_m_b_e_r decimal digits to form filenames for the file pieces. The default is 2. The arguments (_a_r_g_1..._a_r_g_n) to _cccc_ssss_pppp_llll_iiii_tttt can be a combination of the following: PPPPaaaaggggeeee 1111 ccccsssspppplllliiiitttt((((1111)))) ccccsssspppplllliiiitttt((((1111)))) /_r_e_x_p/ A file is to be created for the section from the current line up to (but not including) the line containing the regular expression _r_e_x_p. The line containing _r_e_x_p becomes the current line. This argument may be followed by an optional _++++ or _---- some number of lines (for example, _////_PPPP_aaaa_gggg_eeee_////_----_5555). See _eeee_dddd(1) for a description of how to specify a regular expression. %_r_e_x_p% This argument is the same as /_r_e_x_p/, except that no file is created for the section. _l_n_n_o A file is to be created from the current line up to (but not including) _l_n_n_o. _l_n_n_o becomes the current line. {_n_u_m} Repeat argument. This argument may follow any of the above arguments. If it follows a _r_e_x_p type argument, that argument is applied _n_u_m more times. If it follows _l_n_n_o, the file will be split every _l_n_n_o lines (_n_u_m times) from that point. Enclose all _r_e_x_p type arguments that contain blanks or other characters meaningful to the shell in the appropriate quotes. Regular expressions may not contain embedded new-lines. _cccc_ssss_pppp_llll_iiii_tttt does not affect the original file; it is the user's responsibility to remove it if it is no longer wanted. EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS _cccc_ssss_pppp_llll_iiii_tttt _----_ffff _cccc_oooo_bbbb_oooo_llll _ffff_iiii_llll_eeee _''''_////_pppp_rrrr_oooo_cccc_eeee_dddd_uuuu_rrrr_eeee _dddd_iiii_vvvv_iiii_ssss_iiii_oooo_nnnn_////_'''' _////_pppp_aaaa_rrrr_5555_...._//// _////_pppp_aaaa_rrrr_1111_6666_...._//// This example creates four files, _cccc_oooo_bbbb_oooo_llll_0000_0000..._cccc_oooo_bbbb_oooo_llll_0000_3333. After editing the ``split'' files, they can be recombined as follows: _cccc_aaaa_tttt _cccc_oooo_bbbb_oooo_llll_0000_[[[[_0000_----_3333_]]]] _>>>> _ffff_iiii_llll_eeee Note that this example overwrites the original file. _cccc_ssss_pppp_llll_iiii_tttt _----_kkkk _ffff_iiii_llll_eeee _1111_0000_0000 _{{{{_9999_9999_}}}} This example splits the file at every 100 lines, up to 10,000 lines. The _----_kkkk option causes the created files to be retained if there are less than 10,000 lines; however, an error message would still be printed. _cccc_ssss_pppp_llll_iiii_tttt _----_kkkk _pppp_rrrr_oooo_gggg_...._cccc _''''_%%%%_mmmm_aaaa_iiii_nnnn_((((_%%%%_'''' _''''_////_^^^^_}}}}_////_++++_1111_'''' _{{{{_2222_0000_}}}} If _pppp_rrrr_oooo_gggg_...._cccc follows the normal C coding convention (the last line of a routine consists only of a _}}}} in the first character position), this example creates a file for each separate C routine (up to 21) in _pppp_rrrr_oooo_gggg_...._cccc. FFFFIIIILLLLEEEESSSS _////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee_////_l_o_c_a_l_e_////_LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS_////_uuuu_xxxx_dddd_ffff_mmmm language-specific message file (See _LLLL_AAAA_NNNN_GGGG on _eeee_nnnn_vvvv_iiii_rrrr_oooo_nnnn(5).) PPPPaaaaggggeeee 2222 ccccsssspppplllliiiitttt((((1111)))) ccccsssspppplllliiiitttt((((1111)))) SSSSEEEEEEEE AAAALLLLSSSSOOOO ed(1), sh(1), regexp(5). DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS Self-explanatory except for: _a_r_g - out of range which means that the given argument did not reference a line between the current position and the end of the file. PPPPaaaaggggeeee 3333